SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Software regression</title>

</head>

Software regression

</h1>

</header>

A software regression is a type of <a href="Software_bug" title="Software bug">software bug</a> where a feature that has worked before stops working. This may happen after changes are applied to the software's <a href="Source_code" title="Source code">source code</a>, including the addition of new <a href="Software_feature" title="Software feature">features</a> and bug fixes.<a href="#cite_note-wong-issre-97-1">[1]</a> They may also be introduced by changes to the environment in which the software is running, such as system upgrades, <a href="Patch_(computing)" title="Patch (computing)">system patching</a> or a change to <a href="Daylight_saving_time" title="Daylight saving time">daylight saving time</a>.<a href="#cite_note-ibm-locating-bugs-2">[2]</a> A software performance regression is a situation where the software still functions correctly, but performs more slowly or uses more memory or resources than before.<a href="#cite_note-3">[3]</a> Various types of software regressions have been identified in practice, including the following:<a href="#cite_note-4">[4]</a>

<ul><li>Local – a change introduces a new bug in the changed module or component.</li>

<li>Remote – a change in one part of the software breaks functionality in another module or component.</li>

<li>Unmasked – a change unmasks an already existing bug that had no effect before the change.</li></ul>

Regressions are often caused by <a href="Hotfix" title="Hotfix">encompassed bug fixes</a> included in <a href="Software_patch" class="mw-redirect" title="Software patch">software patches</a>. One approach to avoiding this kind of problem is <a href="Regression_testing" title="Regression testing">regression testing</a>. A properly designed <a href="Test_plan" title="Test plan">test plan</a> aims at preventing this possibility before releasing any software.<a href="#cite_note-5">[5]</a> <a href="Automated_testing" class="mw-redirect" title="Automated testing">Automated testing</a> and well-written <a href="Test_case" title="Test case">test cases</a> can reduce the likelihood of a regression.

<div class="mw-heading mw-heading2"><h2 id="Prevention_and_detection">Prevention and detection</h2></div>

Techniques have been proposed that try to prevent regressions from being introduced into software at various stages of development, as outlined below.

<div class="mw-heading mw-heading3"><h3 id="Prior_to_release">Prior to release</h3></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Regression_testing" title="Regression testing">Regression testing</a></div>

In order to avoid regressions being seen by the <a href="End-user" class="mw-redirect" title="End-user">end-user</a> after release, developers regularly run <a href="Regression_tests" class="mw-redirect" title="Regression tests">regression tests</a> after changes are introduced to the software. These tests can include <a href="Unit_tests" class="mw-redirect" title="Unit tests">unit tests</a> to catch local regressions as well as <a href="Integration_tests" class="mw-redirect" title="Integration tests">integration tests</a> to catch remote regressions.<a href="#cite_note-6">[6]</a> Regression testing techniques often leverage existing test cases to minimize the effort involved in creating them.<a href="#cite_note-7">[7]</a> However, due to the volume of these existing tests, it is often necessary to select a representative subset, using techniques such as <a href="Regression_testing#Test_case_prioritization" title="Regression testing">test-case prioritization</a>.

For detecting performance regressions, <a href="Software_performance_testing" title="Software performance testing">software performance tests</a> are run on a regular basis, to monitor the response time and resource usage metrics of the software after subsequent changes.<a href="#cite_note-8">[8]</a> Unlike functional regression tests, the results of performance tests are subject to <a href="Variance" title="Variance">variance</a> - that is, results can differ between tests due to variance in performance measurements; as a result, a decision must be made on whether a change in performance numbers constitutes a regression, based on experience and end-user demands. Approaches such as <a href="Statistical_significance_test" class="mw-redirect" title="Statistical significance test">statistical significance testing</a> and <a href="Change_point_detection" class="mw-redirect" title="Change point detection">change point detection</a> are sometimes used to aid in this decision.<a href="#cite_note-9">[9]</a>

<div class="mw-heading mw-heading3"><h3 id="Prior_to_commit">Prior to commit</h3></div>

Since <a href="Debugging" title="Debugging">debugging</a> and localizing the root cause of a software regression can be expensive,<a href="#cite_note-10">[10]</a><a href="#cite_note-11">[11]</a> there also exist some methods that try to prevent regressions from being committed into the <a href="Code_repository" class="mw-redirect" title="Code repository">code repository</a> in the first place. For example, <a href="Git" title="Git">Git</a> Hooks enable developers to run test scripts before code changes are committed or pushed to the code repository.<a href="#cite_note-12">[12]</a> In addition, <a href="Change_impact_analysis" title="Change impact analysis">change impact analysis</a> has been applied to software to predict the impact of a code change on various components of the program, and to supplement test case selection and prioritization.<a href="#cite_note-13">[13]</a><a href="#cite_note-14">[14]</a> <a href="Lint_(software)" title="Lint (software)">Software linters</a> are also often added to commit hooks to ensure consistent coding style, thereby minimizing stylistic issues that can make the software prone to regressions.<a href="#cite_note-15">[15]</a>

<div class="mw-heading mw-heading2"><h2 id="Localization">Localization</h2></div>

Many of the techniques used to find the root cause of non-regression software bugs can also be used to debug software regressions, including <a href="Breakpoint" title="Breakpoint">breakpoint debugging</a>, print debugging, and <a href="Program_slicing" title="Program slicing">program slicing</a>. The techniques described below are often used specifically to debug software regressions.

<div class="mw-heading mw-heading3"><h3 id="Functional_regressions">Functional regressions</h3></div>

A common technique used to localize functional regressions is <a href="Bisection_(software_engineering)" title="Bisection (software engineering)">bisection</a>, which takes both a buggy commit and a previously working commit as input, and tries to find the root cause by doing a binary search on the commits in between.<a href="#cite_note-16">[16]</a> <a href="Version_control" title="Version control">Version control</a> systems such as Git and <a href="Mercurial" title="Mercurial">Mercurial</a> provide built-in ways to perform bisection on a given pair of commits.<a href="#cite_note-17">[17]</a><a href="#cite_note-18">[18]</a>

Other options include directly associating the result of a regression test with code changes;<a href="#cite_note-19">[19]</a> setting divergence breakpoints;<a href="#cite_note-20">[20]</a> or using incremental <a href="Data-flow_analysis" title="Data-flow analysis">data-flow analysis</a>, which identifies test cases - including failing ones - that are relevant to a set of code changes,<a href="#cite_note-21">[21]</a> among others.

<div class="mw-heading mw-heading3"><h3 id="Performance_regressions">Performance regressions</h3></div>

<a href="Profiling_(computer_programming)" title="Profiling (computer programming)">Profiling</a> measures the performance and resource usage of various components of a program, and is used to generate data useful in debugging performance issues. In the context of software performance regressions, developers often compare the <a href="Call_stack" title="Call stack">call trees</a> (also known as "timelines") generated by profilers for both the buggy version and the previously working version, and mechanisms exist to simplify this comparison.<a href="#cite_note-22">[22]</a> <a href="Web_development_tools" title="Web development tools">Web development tools</a> typically provide developers the ability to record these performance profiles.<a href="#cite_note-23">[23]</a><a href="#cite_note-24">[24]</a>

Logging also helps with performance regression localization, and similar to call trees, developers can compare systematically-placed performance logs of multiple versions of the same software.<a href="#cite_note-25">[25]</a> A tradeoff exists when adding these performance logs, as adding many logs can help developers pinpoint which portions of the software are regressing at smaller granularities, while adding only a few logs will also reduce overhead when executing the program.<a href="#cite_note-26">[26]</a>

Additional approaches include writing performance-aware unit tests to help with localization,<a href="#cite_note-27">[27]</a> and ranking subsystems based on performance counter deviations.<a href="#cite_note-28">[28]</a> Bisection can also be repurposed for performance regressions by considering commits that perform below (or above) a certain baseline value as buggy, and taking either the left or the right side of the commits based on the results of this comparison.

<ul><li><a href="Software_rot" title="Software rot">Software rot</a></li>

<li><a href="Software_aging" title="Software aging">Software aging</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFWongHorganLondonAgrawal1997" class="citation book cs1">Wong, W. Eric; Horgan, J.R.; London, Saul; Agrawal, Hira (1997). "A Study of Effective Regression Testing in Practice". <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/630875">Proceedings of the Eighth International Symposium on Software Reliability Engineering (ISSRE 97)</a>. IEEE. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FISSRE.1997.630875">10.1109/ISSRE.1997.630875</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-8186-8120-9</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:2911517">2911517</a>.</cite>

</li>

<li id="cite_note-ibm-locating-bugs-2"><a href="#cite_ref-ibm-locating-bugs_2-0">^</a> <cite id="CITEREFYehudaiTyszberowiczNir2007" class="citation conference cs1">Yehudai, Amiram; Tyszberowicz, Shmuel; Nir, Dor (2007). <a rel="nofollow" class="external text" href="https://link.springer.com/chapter/10.1007/978-3-540-77966-7_18#:~:text=Abstract,patch%20causes%20the%20regression%20bug.">Locating Regression Bugs</a>. <a rel="nofollow" class="external text" href="https://www.research.ibm.com/haifa/conferences/hvc2017/previous.shtml">Haifa Verification Conference</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1007%2F978-3-540-77966-7_18">10.1007/978-3-540-77966-7_18</a>. Retrieved 10 March 2018.</cite>

</li>

<li id="cite_note-3"><a href="#cite_ref-3">^</a> <cite id="CITEREFShangHassanNasserFlora2014" class="citation journal cs1">Shang, Weiyi; Hassan, Ahmed E.; Nasser, Mohamed; Flora, Parminder (11 December 2014). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210113231136/https://sail.cs.queensu.ca/Downloads/ICPE2015_AutomatedDetectionofPerformanceRegressionsUsingRegressionModelsOnClusteredPerformanceCounters.pdf#page=1">"Automated Detection of Performance Regressions Using Regression Models on Clustered Performance Counters"</a> (PDF). Archived from <a rel="nofollow" class="external text" href="https://sail.cs.queensu.ca/Downloads/ICPE2015_AutomatedDetectionofPerformanceRegressionsUsingRegressionModelsOnClusteredPerformanceCounters.pdf#page=1">the original</a> (PDF) on 13 January 2021. Retrieved 22 December 2019.</cite> <code class="cs1-code">{{cite journal}}</code>: Cite journal requires <code class="cs1-code">|journal=</code> (help)

</li>

<li id="cite_note-4"><a href="#cite_ref-4">^</a> <cite id="CITEREFHenry2008" class="citation book cs1">Henry, Jean-Jacques Pierre (2008). The Testing Network: An Integral Approach to Test Activities in Large Software Projects. Springer Science & Business Media. p. 74. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-3540785040</bdi>.</cite>

</li>

<li id="cite_note-5"><a href="#cite_ref-5">^</a> <cite id="CITEREFRichardsonGwaltney,_William_Jr2006" class="citation book cs1">Richardson, Jared; Gwaltney, William Jr (2006). <a rel="nofollow" class="external text" href="https://archive.org/details/shipitpracticalg0000rich/page/32">Ship It! A Practical Guide to Successful Software Projects</a>. Raleigh, NC: The Pragmatic Bookshelf. pp. <a rel="nofollow" class="external text" href="https://archive.org/details/shipitpracticalg0000rich/page/32">32, 193</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-9745140-4-8</bdi>.</cite>

</li>

<li id="cite_note-6"><a href="#cite_ref-6">^</a> <cite id="CITEREFLeungWhite1990" class="citation book cs1">Leung, Hareton K.N.; White, Lee (November 1990). "A study of integration testing and software regression at the integration level". <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/131377">Proceedings of the International Conference on Software Maintenance</a>. San Diego, CA, USA: IEEE. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FICSM.1990.131377">10.1109/ICSM.1990.131377</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-8186-2091-9</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:62583582">62583582</a>.</cite>

</li>

<li id="cite_note-7"><a href="#cite_ref-7">^</a> <cite id="CITEREFRothermelHarroldDedhia2000" class="citation journal cs1">Rothermel, Gregg; Harrold, Mary Jean; Dedhia, Jeinay (2000). <a rel="nofollow" class="external text" href="https://onlinelibrary.wiley.com/doi/abs/10.1002/1099-1689(200006)10:2%3C77::AID-STVR197%3E3.0.CO;2-E">"Regression test selection for C++ software"</a>. Software Testing, Verification and Reliability. 10 (2): 77–109. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1002%2F1099-1689%28200006%2910%3A2%3C77%3A%3AAID-STVR197%3E3.0.CO%3B2-E">10.1002/1099-1689(200006)10:2<77::AID-STVR197>3.0.CO;2-E</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1099-1689">1099-1689</a>.</cite>

</li>

<li id="cite_note-8"><a href="#cite_ref-8">^</a> <cite id="CITEREFWeyukerVokolos2000" class="citation journal cs1">Weyuker, E.J.; Vokolos, F.I. (December 2000). <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/888628">"Experience with performance testing of software systems: issues, an approach, and case study"</a>. IEEE Transactions on Software Engineering. 26 (12): 1147–1156. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2F32.888628">10.1109/32.888628</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1939-3520">1939-3520</a>.</cite>

</li>

<li id="cite_note-9"><a href="#cite_ref-9">^</a> <cite id="CITEREFDalyBrownIngoO'Leary2020" class="citation book cs1">Daly, David; Brown, William; Ingo, Henrik; O'Leary, Jim; Bradford, David (20 April 2020). "The Use of Change Point Detection to Identify Software Performance Regressions in a Continuous Integration System". <a rel="nofollow" class="external text" href="https://dl.acm.org/doi/abs/10.1145/3358960.3375791">Proceedings of the International Conference on Performance Engineering</a>. Association for Computing Machinery. pp. 67–75. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F3358960.3375791">10.1145/3358960.3375791</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4503-6991-6</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:211677818">211677818</a>.</cite>

</li>

<li id="cite_note-10"><a href="#cite_ref-10">^</a> <cite id="CITEREFNistorJiangTan2013" class="citation book cs1">Nistor, Adrian; Jiang, Tian; Tan, Lin (May 2013). "Discovering, reporting, and fixing performance bugs". <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/6624035">Proceedings of the Working Conference on Mining Software Repositories (MSR)</a>. pp. 237–246. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FMSR.2013.6624035">10.1109/MSR.2013.6624035</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4673-2936-1</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:12773088">12773088</a>.</cite>

</li>

<li id="cite_note-11"><a href="#cite_ref-11">^</a> <cite id="CITEREFAgarwalAgrawal2014" class="citation journal cs1">Agarwal, Pragya; Agrawal, Arun Prakash (17 September 2014). <a rel="nofollow" class="external text" href="https://dl.acm.org/doi/abs/10.1145/2659118.2659125">"Fault-localization techniques for software systems: a literature review"</a>. ACM SIGSOFT Software Engineering Notes. 39 (5): 1–8. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F2659118.2659125">10.1145/2659118.2659125</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/0163-5948">0163-5948</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:12101263">12101263</a>.</cite>

</li>

<li id="cite_note-12"><a href="#cite_ref-12">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks">"Git - Git Hooks"</a>. git-scm.com. Retrieved 7 November 2021.</cite>

</li>

<li id="cite_note-13"><a href="#cite_ref-13">^</a> <cite id="CITEREFOrsoApiwattanapongHarrold2003" class="citation journal cs1">Orso, Alessandro; Apiwattanapong, Taweesup; Harrold, Mary Jean (1 September 2003). <a rel="nofollow" class="external text" href="https://dl.acm.org/doi/abs/10.1145/949952.940089">"Leveraging field data for impact analysis and regression testing"</a>. ACM SIGSOFT Software Engineering Notes. 28 (5): 128–137. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F949952.940089">10.1145/949952.940089</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/0163-5948">0163-5948</a>.</cite>

</li>

<li id="cite_note-14"><a href="#cite_ref-14">^</a> <cite id="CITEREFQuAcharyaRobinson2012" class="citation book cs1">Qu, Xiao; Acharya, Mithun; Robinson, Brian (September 2012). "Configuration selection using code change impact analysis for regression testing". <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/6405263">Proceedings of the International Conference on Software Maintenance</a>. pp. 129–138. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FICSM.2012.6405263">10.1109/ICSM.2012.6405263</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4673-2312-3</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:14928793">14928793</a>.</cite>

</li>

<li id="cite_note-15"><a href="#cite_ref-15">^</a> <cite id="CITEREFTómasdóttirAnichevan_Deursen2017" class="citation book cs1">Tómasdóttir, Kristín Fjóla; Aniche, Mauricio; van Deursen, Arie (October 2017). "Why and how JavaScript developers use linters". <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/8115668">Proceedings of the International Conference on Automated Software Engineering</a>. pp. 578–589. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FASE.2017.8115668">10.1109/ASE.2017.8115668</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-5386-2684-9</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:215750004">215750004</a>.</cite>

</li>

<li id="cite_note-16"><a href="#cite_ref-16">^</a> <cite id="CITEREFGross1997" class="citation book cs1">Gross, Thomas (10 September 1997). "Bisection Debugging". <a rel="nofollow" class="external text" href="https://ep.liu.se/en/conference-article.aspx?series=ecp&issue=1&Article_No=15">Proceedings of the International Workshop on Automatic Debugging</a>. Linkøping University Electronic Press. pp. 185–191.</cite>

</li>

<li id="cite_note-17"><a href="#cite_ref-17">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://git-scm.com/docs/git-bisect">"Git - git-bisect Documentation"</a>. git-scm.com. Retrieved 7 November 2021.</cite>

</li>

<li id="cite_note-18"><a href="#cite_ref-18">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.selenic.com/mercurial/hg.1.html">"hg - bisect"</a>. www.selenic.com. Mercurial. Retrieved 7 November 2021.</cite>

</li>

<li id="cite_note-19"><a href="#cite_ref-19">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.mit.edu/6.005/www/fa15/classes/11-debugging/">"Reading 11: Debugging"</a>. web.mit.edu. MIT.</cite>

</li>

<li id="cite_note-20"><a href="#cite_ref-20">^</a> <cite id="CITEREFBuhseWeiZangMilicevic2019" class="citation book cs1">Buhse, Ben; Wei, Thomas; Zang, Zhiqiang; Milicevic, Aleksandar; Gligoric, Milos (May 2019). "VeDebug: Regression Debugging Tool for Java". <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/8802682">Proceedings of the International Conference on Software Engineering: Companion Proceedings (ICSE-Companion)</a>. pp. 15–18. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FICSE-Companion.2019.00027">10.1109/ICSE-Companion.2019.00027</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-7281-1764-5</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:174799830">174799830</a>.</cite>

</li>

<li id="cite_note-21"><a href="#cite_ref-21">^</a> <cite id="CITEREFTahaThebautLiu1989" class="citation book cs1">Taha, A.-B.; Thebaut, S.M.; Liu, S.-S. (September 1989). "An approach to software fault localization and revalidation based on incremental data flow analysis". <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/65142">Proceedings of the Annual International Computer Software & Applications Conference</a>. IEEE. pp. 527–534. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FCMPSAC.1989.65142">10.1109/CMPSAC.1989.65142</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-8186-1964-3</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:41978046">41978046</a>.</cite>

</li>

<li id="cite_note-22"><a href="#cite_ref-22">^</a> <cite id="CITEREFOcarizaZhao2021" class="citation journal cs1">Ocariza, Frolin S.; Zhao, Boyang (2021). <a rel="nofollow" class="external text" href="https://onlinelibrary.wiley.com/doi/abs/10.1002/stvr.1750">"Localizing software performance regressions in web applications by comparing execution timelines"</a>. Software Testing, Verification and Reliability. 31 (5): e1750. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1002%2Fstvr.1750">10.1002/stvr.1750</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1099-1689">1099-1689</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:225416138">225416138</a>.</cite>

</li>

<li id="cite_note-23"><a href="#cite_ref-23">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://developer.chrome.com/docs/devtools/evaluate-performance/">"Analyze runtime performance"</a>. Chrome Developers. Google. Retrieved 7 November 2021.</cite>

</li>

<li id="cite_note-24"><a href="#cite_ref-24">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://docs.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/evaluate-performance/reference">"Performance analysis reference - Microsoft Edge Development"</a>. docs.microsoft.com. Microsoft. Retrieved 7 November 2021.</cite>

</li>

<li id="cite_note-25"><a href="#cite_ref-25">^</a> <cite id="CITEREFYaoB._de_PáduaShangSporea2018" class="citation book cs1">Yao, Kundi; B. de Pádua, Guilherme; Shang, Weiyi; Sporea, Steve; Toma, Andrei; Sajedi, Sarah (30 March 2018). "Log4Perf: Suggesting Logging Locations for Web-based Systems' Performance Monitoring". <a rel="nofollow" class="external text" href="https://dl.acm.org/doi/abs/10.1145/3184407.3184416">Proceedings of the International Conference on Performance Engineering</a>. Association for Computing Machinery. pp. 127–138. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F3184407.3184416">10.1145/3184407.3184416</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4503-5095-2</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:4557038">4557038</a>.</cite>

</li>

<li id="cite_note-26"><a href="#cite_ref-26">^</a> <cite id="CITEREFLiShangAdamsSayagh2020" class="citation journal cs1">Li, Heng; Shang, Weiyi; Adams, Bram; Sayagh, Mohammed; Hassan, Ahmed E. (30 January 2020). <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/8976297">"A Qualitative Study of the Benefits and Costs of Logging from Developers' Perspectives"</a>. IEEE Transactions on Software Engineering. 47 (12): 2858–2873. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FTSE.2020.2970422">10.1109/TSE.2020.2970422</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:213679706">213679706</a>.</cite>

</li>

<li id="cite_note-27"><a href="#cite_ref-27">^</a> <cite id="CITEREFHegerHappeFarahbod2013" class="citation book cs1">Heger, Christoph; Happe, Jens; Farahbod, Roozbeh (21 April 2013). "Automated root cause isolation of performance regressions during software development". <a rel="nofollow" class="external text" href="https://dl.acm.org/doi/abs/10.1145/2479871.2479879">Proceedings of the International Conference on Performance Engineering</a>. Association for Computing Machinery. pp. 27–38. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F2479871.2479879">10.1145/2479871.2479879</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4503-1636-1</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:2593603">2593603</a>.</cite>

</li>

<li id="cite_note-28"><a href="#cite_ref-28">^</a> <cite id="CITEREFMalikAdamsHassan2010" class="citation book cs1">Malik, Haroon; Adams, Bram; Hassan, Ahmed E. (November 2010). "Pinpointing the Subsystems Responsible for the Performance Deviations in a Load Test". <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/5635038">Proceedings of the International Symposium on Software Reliability Engineering</a>. pp. 201–210. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FISSRE.2010.43">10.1109/ISSRE.2010.43</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4244-9056-1</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:17306870">17306870</a>.</cite>

</li>

</ol></div></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-05-23" href="https://en.wikipedia.org/wiki/?title=Software_regression&oldid=1291800130">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>